Configurable plug-in architecture for manipulating xml-formatted information

ABSTRACT

A method and system is described for building a document using a configurable plug-in architecture. In one example, a configuration file containing information of building the document with one or more components is received. The one or more components execute to modify or manipulate the document. The document may further be passed from one component to another component, where each of the components performs a function on the document. The sequence of execution of the components, the type of function or activity executed by each of the components, and/or configuration data of the components may be provided by the configuration file. The document may further be output to a user or stored.

CROSS-REFERENCE TO RELATED APPLICATION

This application claims the benefit of U.S. Provisional PatentApplication Ser. No. 60/945,552, filed Jun. 21, 2007, entitled“CONFIGURABLE PLUG-IN ARCHITECTURE FOR MANIPULATING XML-FORMATTEDINFORMATION” which is incorporated herein by reference in its entirety.

BACKGROUND

The creation and management of documents in any of a number of formatshas become commonplace. These documents may range from free-form tohighly structured data structures, schemas, etc. Also the documents maybe generated based on information from different sources or input files.

However, typically document build systems lack the capacity toefficiently provide arbitrary output formats or to draw on multipleinput files. Previous document build systems consist of a singlemonolithic application that generates a fixed sort of documentation froma fixed set of inputs. Such build systems do not allow the entire buildlogic to be changed in arbitrary ways. These systems and methods alsolack versatility to effectively create documents of any type undervariable scenarios. Thus, there is a need for a system or method withflexibility to manage different document scenarios as well as remainsufficiently unified to present a uniform interface for a user.

SUMMARY

The following presents a simplified summary of the disclosure in orderto provide a basic understanding to the reader. This summary is not anextensive overview of the disclosure and it does not identifykey/critical elements of the invention or delineate the scope of theinvention. Its sole purpose is to present some concepts disclosed hereinin a simplified form as a prelude to the more detailed description thatis presented later.

In one example, a method for generating a document is described in whicha component or group of components are used to modify a document basedon a configuration file. For example, a first component and a secondcomponent may execute a function or action on a document in a sequencebased on the configuration file.

In another example, the order or sequence of execution of the componentsmay be modified. For example, the configuration file may be modifiedwhich may cause a corresponding change in the order of execution of thecomponents in the generation of the document.

In yet another example, a plurality of components for modifying ormanipulating a document is assembled based on a configuration file. Eachof the components may execute a function or action on the document in asequence indicated by the configuration file.

Many of the attendant features will be more readily appreciated as thesame becomes better understood by reference to the following detaileddescription considered in connection with the accompanying drawings.

DESCRIPTION OF THE DRAWINGS

The present description will be better understood from the followingdetailed description read in light of the accompanying drawings,wherein:

FIG. 1 illustrates an example of a suitable computing systemenvironment.

FIG. 2 is a block diagram illustrating one example of a system or buildengine for creating output documents.

FIG. 3 is a block diagram illustrating another example of a system orbuild engine for a documentation build.

FIG. 4 illustrates an example of a configuration file.

FIG. 5 illustrates an example of a pseudo-header.

FIG. 6 is a flowchart illustrating an example of a process for adocument build.

Like reference numerals are used to designate like parts in theaccompanying drawings.

DETAILED DESCRIPTION

The detailed description provided below in connection with the appendeddrawings is intended as a description of the present examples and is notintended to represent the only forms in which the present example may beconstructed or utilized. The description sets forth the functions of theexample and the sequence of steps for constructing and operating theexample. However, the same or equivalent functions and sequences may beaccomplished by different examples. Systems described herein areprovided as examples and not limitations. As those skilled in the artwill appreciate, the present examples are suitable for application in avariety of different types of computing systems.

FIG. 1 illustrates an example of a suitable computing system environmentor architecture in which computing subsystems may provide processingfunctionality. The computing system environment is only one example of asuitable computing environment and is not intended to suggest anylimitation as to the scope of use or functionality of the invention.Neither should the computing environment be interpreted as having anydependency or requirement relating to any one or combination ofcomponents illustrated in the exemplary operating environment.

The method or system disclosed herein is operational with numerous othergeneral purpose or special purpose computing system environments orconfigurations. Examples of well known computing systems, environments,and/or configurations that may be suitable for use with the inventioninclude, but are not limited to, personal computers, server computers,hand-held or laptop devices, multiprocessor systems,microprocessor-based systems, set top boxes, programmable consumerelectronics, network PCs, minicomputers, mainframe computers,distributed computing environments that include any of the above systemsor devices, and the like.

The method or system may be described in the general context ofcomputer-executable instructions, such as program modules, beingexecuted by a computer. Generally, program modules include routines,programs, objects, components, data structures, etc. that performparticular tasks or implement particular abstract data types. The methodor system may also be practiced in distributed computing environmentswhere tasks are performed by remote processing devices that are linkedthrough a communications network. In a distributed computingenvironment, program modules may be located in both local and remotecomputer storage media including memory storage devices.

With reference to FIG. 1, an exemplary system for implementing themethod or system includes a general purpose computing device in the formof a computer 102. Components of computer 102 may include, but are notlimited to, a processing unit 104, a system memory 106, and a system bus108 that couples various system components including the system memoryto the processing unit 104. The system bus 108 may be any of severaltypes of bus structures including a memory bus or memory controller, aperipheral bus, and a local bus using any of a variety of busarchitectures. By way of example, and not limitation, such architecturesinclude Industry Standard Architecture (ISA) bus, Micro ChannelArchitecture (MCA) bus, Enhanced ISA (EISA) bus, Video ElectronicsStandards Association (VESA) local bus, and Peripheral ComponentInterconnect (PCI) bus also known as Mezzanine bus.

Computer 102 typically includes a variety of computer readable media.Computer readable media can be any available media that can be accessedby computer 102 and includes both volatile and nonvolatile media,removable and non-removable media. By way of example, and notlimitation, computer readable media may comprise computer storage media.Computer storage media includes both volatile and nonvolatile, removableand non-removable media implemented in any method or technology forstorage of information such as computer readable instructions, datastructures, program modules or other data. Computer storage mediaincludes, but is not limited to, RAM, ROM, EEPROM, flash memory or othermemory technology, CD-ROM, digital versatile disks (DVD) or otheroptical disk storage, magnetic cassettes, magnetic tape, magnetic diskstorage or other magnetic storage devices, or any other medium which canbe used to store the desired information and which can accessed bycomputer 102. Combinations of the any of the above should also beincluded within the scope of computer readable storage media.

The system memory 106 includes computer storage media in the form ofvolatile and/or nonvolatile memory such as read only memory (ROM) 110and random access memory (RAM) 112. A basic input/output system 114(BIOS), containing the basic routines that help to transfer informationbetween elements within computer 102, such as during start-up, istypically stored in ROM 110. RAM 112 typically contains data and/orprogram modules that are immediately accessible to and/or presentlybeing operated on by processing unit 104. By way of example, and notlimitation, FIG. 1 illustrates operating system 132, applicationprograms 134, other program modules 136, and program data 138.

The computer 102 may also include other removable/non-removable,volatile/nonvolatile computer storage media. By way of example only,FIG. 1 illustrates a hard disk drive 116 that reads from or writes tonon-removable, nonvolatile magnetic media, a magnetic disk drive 118that reads from or writes to a removable, nonvolatile magnetic disk 120,and an optical disk drive 122 that reads from or writes to a removable,nonvolatile optical disk 124 such as a CD ROM or other optical media.Other removable/non-removable, volatile/nonvolatile computer storagemedia that can be used in the exemplary operating environment include,but are not limited to, magnetic tape cassettes, flash memory cards,digital versatile disks, digital video tape, solid state RAM, solidstate ROM, and the like. The hard disk drive 116 is typically connectedto the system bus 108 through a non-removable memory interface such asinterface 126, and magnetic disk drive 118 and optical disk drive 122are typically connected to the system bus 108 by a removable memoryinterface, such as interface 128 or 130.

The drives and their associated computer storage media discussed aboveand illustrated in FIG. 1, provide storage of computer readableinstructions, data structures, program modules and other data for thecomputer 102. In FIG. 1, for example, hard disk drive 116 is illustratedas storing operating system 132, application programs 134, other programmodules 136, and program data 138. Note that these components can eitherbe the same as or different from additional operating systems,application programs, other program modules, and program data, forexample, different copies of any of the elements. A user may entercommands and information into the computer 102 through input devicessuch as a keyboard 140 and pointing device 142, commonly referred to asa mouse, trackball or touch pad. Other input devices (not shown) mayinclude a microphone, joystick, game pad, pen, scanner, or the like.These and other input devices are often connected to the processing unit104 through a user input interface 144 that is coupled to the systembus, but may be connected by other interface and bus structures, such asa parallel port, game port or a universal serial bus (USB). A monitor158 or other type of display device is also connected to the system bus108 via an interface, such as a video interface or graphics displayinterface 156. In addition to the monitor 158, computers may alsoinclude other peripheral output devices such as speakers (not shown) andprinter (not shown), which may be connected through an output peripheralinterface (not shown).

The computer 102 may operate in a networked environment using logicalconnections to one or more remote computers, such as a remote computer.The remote computer may be a personal computer, a server, a router, anetwork PC, a peer device or other common network node, and typicallyincludes many or all of the elements described above relative to thecomputer 102. The logical connections depicted in FIG. 1 include a localarea network (LAN) 148 and a wide area network (WAN) 150, but may alsoinclude other networks. Such networking environments are commonplace inoffices, enterprise-wide computer networks, intranets and the Internet.

When used in a LAN networking environment, the computer 102 is connectedto the LAN 148 through a network interface or adapter 152. When used ina WAN networking environment, the computer 102 typically includes amodem 154 or other means for establishing communications over the WAN150, such as the Internet. The modem 154, which may be internal orexternal, may be connected to the system bus 108 via the user inputinterface 144, or other appropriate mechanism. In a networkedenvironment, program modules depicted relative to the computer 102, orportions thereof, may be stored in the remote memory storage device. Byway of example, and not limitation, remote application programs mayreside on a memory device. It will be appreciated that the networkconnections shown are exemplary and other means of establishing acommunications link between the computers may be used.

In one example, a build engine may create documents of any type ornumber. For example, documents may include any free-form topic createdby an author, a structured API, a schema, a protocol reference, etc. Thefollowing description is applicable to any form of document building. Inaddition, an output document may include information based on any numberor type of sources. For example, an output document may includeinformation derived from any number of multiple input files, authoredsource files, code sample files, or files containing API, schema orprotocol metadata, to name a few.

In this example, a build engine or other system is described that mayreceive any number or type of output files to generate. For example, thebuild engine may receive a configuration file that may describe steps tobe executed to produce a desired output document or any other suchpertinent information for the build engine. The configuration file mayalso contain information for specifying components to be loaded orutilized in a document build, specifying the order in which componentsoperate, and/or providing configuration data for any of the components.

The build engine in this example may execute any number of steps forbuilding a document. The steps may be executed in an order or sequenceas indicated by corresponding configuration data in a configurationfile. Also, each of the steps executed for building the document may beexecuted by any number or type of components in the build engine thatmay act in an arbitrary fashion on the document. For example, a firstcomponent in the build engine may receive a document and, based oninformation in the configuration file, may perform a desired function oraction on the document to manipulate or modify the document. The firstcomponent may pass the modified document to a second component, whichmay also be indicated by at least a portion of the configuration data.The second component may receive the modified document from the firstcomponent and may perform an action or function on the received modifieddocument. The action or function performed by the second component onthe received modified document may, for example, be determined by atleast a portion of data in the configuration file. The process may berepeated such that the document may be modified or manipulated by anynumber of components in a sequence to produce an output document.

In another example, the sequence of execution of the components in thebuild engine may be modified. Also, the functions or actions executed byany of the components may be modified such that a single component mayperform any number and type of different functions or actions on adocument. In this example, configuration data or settings of a componentmay be modified such that the component may perform a different functionor action. In this case, a first component may modify a document basedon configuration data and may further perform a different modificationto the document based on different configuration data. Thus, in thisexample, the action of any individual component may be changed and anyindividual component may be reused with different configuration settingsto perform a different function.

In another example, output files may be created and may be changedwithout requiring that the system be re-compiled. Also, any of the stepsin the creation of the output file may be configured withoutre-compiling either the system or the step logic. In addition, a uniformframework may be used to control any of the variable aspects.

An engine may accept an arbitrary list of output files for generation.FIG. 2 is a block diagram illustrating one example of a system or buildengine for creating output documents. In this example, the systemincludes an input 201 for receiving an arbitrary list of output files togenerate. The arbitrary list of output files are analyzed in theanalyzer 202 in which a configuration file may be read from aconfiguration module 203. Hence, in this example, the analyzer 202receives a configuration file from the configuration module 203. Theconfiguration file (not shown) may include information pertaining tooutput files. For example, the configuration file may include datacorresponding to a sequence of steps to be performed for each outputfile. The steps may be executed, for example, by a file generator 204that may produce a desired output document. In this example, the filegenerator 204 may include any number of component processors (not shown)that may receive a document from a previous component processor andexecute an add-in component that may act in an arbitrary fashion on thereceived document. The component processor of the file generator 204 mayfurther pass the document to a next component processor for furtherprocessing.

Any of the add-in components may be modified such that the steps forconstructing a given document may be varied in any number of ways. Forexample, the order of components in a configuration file may be changed.In this example, a component may read configuration data in aconfiguration file. The configuration data that is read may furtherdetermine an action by the component.

FIG. 3 is a block diagram illustrating another example of a system orbuild engine for a documentation build. In this example, informationfrom a configuration module 304 may be used to build a document in acomponent constructor 305. For example, a configuration file may specifycomponents to be loaded or the order in which the components operate,and/or configuration data for any component, to name a few. AlthoughFIG. 3 illustrates three add-in components (301-303), any number ofadd-in components (e.g., Add-in component 301, 302, and/or 303) mayprovide objects representing respective component elements.

In this example, the configuration module 304 provides a configurationfile for determining an order of add-in components and the action orfunction of the add-in components. Also, the configuration file maycontain configuration data pertaining to each of the add-in components.The component constructor 305 may receive an object from an add-incomponent (e.g., add-in component 301) based on data in theconfiguration file. For example, the configuration file may indicatethat add-in component 301 is the first component for performing adesired action or function on a document. Also, the configuration filemay provide configuration settings for add-in component 301 forperforming the desired action or function.

The component constructor 305 in this example may receive an object fromadd-in component 301 which may include, for example, a componentelement. The component constructor 305 may use the object received fromthe add-in component 301 to read configuration data from theconfiguration module 304. In addition, a document may be created in thecomponent constructor 305 corresponding to an output document. Forexample, the document may include an editable document (e.g., XMLdocument) and/or a string for indicating a topic being built. An add-incomponent (e.g., add-in component 301) may be added as a componentelement by the component constructor. The add-in component (e.g., add-incomponent 301) may include a module for manipulating or managing adocument based on configuration data and may further pass themanipulated document to another component or add-in component. The othercomponent may receive the manipulated document from the first componentand may further manipulate or manage the document to create an outputdocument or may pass the document to yet another component or componentelement.

In this example, based on the configuration file from the configurationmodule 304, add-in components may pass corresponding objects andcomponent elements to the component constructor 305. The configurationfile may further determine the sequence of execution of the add-incomponents. Hence, based on this information in the configuration file,each of the add-in components may perform a corresponding function oraction on a document. Each of the actions or functions associated withthe add-in component may be executed in a sequence that may be indicatedby at least a portion of the configuration file. In one example toillustrate, the configuration file may indicate that the add-incomponents execute respective functions or actions on a document suchthat add-in component 301 performs an action first, add-in component 302performs an action second and add-in component 303 performs an actionthird. The configuration file may further provide configuration settingsfor each of the add-in components to perform the respective functions oractions. Based on the configuration file, add-in component 301 mayperform its action on a document first and may subsequently pass thedocument to the second add-in component 302. Add-in component 302 mayperform its action/function on the document received from the firstadd-in component 301 and subsequently pass the document to the thirdadd-in component 303. The third add-in component 303 may receive thedocument from the second add-in component 302 and may further perform anaction or function on the document. After each of the componentsperforms a desired function or activity on the document, the documentmay be sent to an output 306 and may be output to a user. Alternativelyor additionally, the document may be stored in memory or a storagedevice.

In another example, any of the add-in components may be re-configured orremoved. For example, the configuration file from the configurationmodule 304 may be modified to indicate a different sequence of actionsto be performed on a document. As one example to illustrate, theconfiguration file may contain data that indicates add-in component 302to perform a function or action on the document first followed by add-incomponent 301. In this case, add-in component 302 performs a function onthe document prior to add-in component 301. Add-in component 302 may,for example, send an object representing an associated component elementto the component constructor 305. The component constructor 305 receivesthe object from add-in component 302 and may further execute an actionor function on the received object based on the add-in component 302 andinformation from the configuration file. For example, the configurationfile may include data indicating that add-in component 302 executes aparticular step in a document build. Based on the data in theconfiguration file, the add-in component 302 may send an associatedobject to the component constructor 305 to execute an action or functionon the document and pass the document to a next component, if desired.

In this example, add-in component 302 may modify the document based onexecution of the component. Add-in component 302 may further pass themodified document to add-in component 301 in the system for furtherprocessing. Any of the steps executed by any of the components may bebased on information in the configuration file. The order of executionof the components may also be modified by modifying the configurationfile. For example, data in the configuration file may be modified toindicate that add-in component 301 executes prior to add-in component302. In that case, the execution of the components may be modifiedaccordingly.

Further, the functions or activities of any of the components may bechanged via the configuration file. For example, the configuration filemay indicate that add-in component 301 perform a first execution on thedocument followed by an execution of a function by add-in component 302.The configuration file may further indicate that add-in component 301performs a second execution on the document following the execution ormodification of the document by add-in component 302. The secondexecution of add-in component 301 may be different from the firstexecution of the add-in component 302. For example, the second executionof add-in component 301 may perform a different function or a differentactivity as that of the first execution of add-in component 301. In thiscase, the functionality of a component may be changed to performdifferent functions as needed.

FIG. 4 illustrates an example of a configuration file. In this example,the configuration file includes an XML file that specifies components tobe loaded, the order in which they operate and the configuration datafor each. Any of the component elements may cause an add-on component ofthe specified type to be instantiated from a specified assembly. Inaddition, the configuration data for the component may be represented aschild nodes of the component element.

In one example to illustrate, a component may include a .NET managedtype that implements an abstract class. For example, the build enginemay include a console application. The console application may furtherdefine the abstract class implemented by each component. In addition, apseudo-header may be used. FIG. 5 illustrates an example of apseudo-header that includes aspects of the abstract class.

The build engine may further include a manifest file including anynumber or type of topic ID strings and may repeat a specified cycle forany number of topics in the manifest file.

In addition, components may be divided into groups based on type. In oneexample, three types of components may be used. For example, one groupof components may include action components for modifying a document.Another group of components may include flow control components forexecuting sub-steps any number of times in any number of differentcircumstances. Another group of components may include diagnosticcomponents for checking the build system and determining if the buildsystem is operating at various arbitrary intermediate points.

The action components may include any number or type of components formodifying the document. For example, action components may include acomponent for copying data from a file. In this example, the componentmay copy a node that is specified by a configurable source XPathexpression from a configurable file. The component may further copy thenode to a node in the document that is specified by a configurabletarget XPath expression.

In another example, the action components may include a component forcopying data from an index. The component in this example may, forexample, maintain an index of source nodes available in a documentstore. Thus, information may be copied from any document as needed whilethe information need not be stored in memory throughout the process. Inaddition, the component in this example may implement a cachingmechanism. In this way, performance can be enhanced.

In another example, the action components may include a component forimplementing logic specific to certain scenarios. For example, acomponent may resolve links to external API reference topics and mayfurther generate link text appropriate to a referenced API.

In another example, the action components may include a component fortransforming data. For example, the component in this example may applya configurable transform (e.g., an XSL transform) and/or associatedconfigurable arguments.

Also, the action components may include a component for saving adocument. The component in this example may further save configurablesubsections of the document to a path constructed via a configurableexpression (e.g., configurable XPath expression).

The components may further include flow control components such as, forexample, a component for executing a configurable set of sub-componentsdepending on a result of a configurable XPath expression (e.g., an“IfThen” component) or a component for executing a configurable set ofsub-components once for each node returned by a configurable XPathexpression (e.g., a “ForEach” component).

Also, the components may further include any number or type ofdiagnostic components. Some non-limiting examples of diagnosticcomponents include a component for writing a document or anyconfigurable subsections thereof, to a log or other storage (e.g., aprint component) or a component for ensuring that a document conforms toa schema specified by a configurable file (e.g., a validationcomponent). For example, the component may be used to ensure that onlystrictly compliant XHTML documentation is generated.

FIG. 6 is a flowchart illustrating an example of a process for adocument build. In this example, configuration data may be received(STEP 401), the configuration data containing any information for anoutput document. The information may include, for example, an indicationfor components in execution of steps in the building of the outputdocument. The components may be add-in components that may be added to abuild engine in a sequence as specified by the configuration data inSTEP 401. In addition, the information may indicate a function oractivity for any of the components. The information in the configurationdata may further be modified or altered such that the components in thedocument build may be modified or altered accordingly.

In STEP 402, a component may be instantiated. In this case, thecomponent instantiated may be based on information in the configurationdata. For example, the configuration may identify a particular add-incomponent to be included in a build engine for performing a desiredfunction or activity. In STEP 403, an object corresponding to theidentified add-in component may be received at the build engine from theadd-in component. In one example, the object received from the add-incomponent may include an editable document (e.g., an XML document) andadditional information (e.g., a data string) to inform the topic beingbuilt.

In STEP 404, a method of a component may be executed to manipulate ormodify the document. The execution may be based on the configurationdata. For example, the configuration data may contain a specification offunctions or activities to be performed on the document, the componentsfor performing the functions, and/or the order or sequence of thecomponents or execution of functions/activities by the components.Hence, based on the configuration data, the output document may bemodified (e.g., by a component).

If additional components are desired (“Yes” branch of STEP 405), thenext component or add-in component may be included in the build engine.In this example, the configuration data may contain an indication of anext component to perform a desired function or activity on the document(STEP 406). As an example to illustrate, a second component may beindicated by the configuration data to perform a transform function onthe document. In this case, the first component may pass the document tothe second component (STEP 407), which may be instantiated in the buildengine (STEP 402) and may pass an associated object (STEP 403) tofurther modify the document (STEP 404).

If a next component is not desired such that further modifications tothe present topic of the document are not desired (“No” branch of STEP405), then a determination of a next topic is made (STEP 408). Forexample, a manifest including a flat file of topic ID strings may beincluded. If a next topic ID string is identified (“Yes” branch of STEP408 and STEP 410), then a component for the next topic may be identifiedbased on the configuration data. The component may be instantiated (STEP402) and the output document may be modified.

As described above, the process may be repeated such that componentsassociated with the next topic may be instantiated to modify ormanipulate the document. In one embodiment, components are instantiatedonce per run of the build engine. The build engine may process multipledocuments in a single run. Thus, a component that has been previouslyinstantiated that is called again by the configuration data is notre-instantiated.

The components may execute functions or actions based on configurationdata from the configuration file and may also execute in a sequencebased on data in the configuration file. When the final topic iscomplete (“No” branch of STEP 408), the output document may be output(STEP 409). Alternatively or additionally, the output document may besaved in memory.

It is understood that aspects of the present description can take manyforms and embodiments. The embodiments shown herein are intended toillustrate rather than to limit the description, it being appreciatedthat variations may be made without departing from the spirit of thescope of the invention. Although illustrative embodiments have beenshown and described, a wide range of modification, change andsubstitution is intended in the foregoing disclosure and in someinstances some features may be employed without a corresponding use ofthe other features. Accordingly, it is appropriate that the examples beconstrued broadly and in a manner consistent with the scope of theinvention.

1. A method of creating a document, the method comprising: receiving aconfiguration file; receiving a first component for modifying a documentbased on information in the configuration file; executing the firstcomponent on the document to modify the document; passing the modifieddocument to a second component based on the configuration file;executing the second component on the modified document to generate anoutput document; and outputting the output document.
 2. The method ofclaim 1 wherein the configuration file indicates a sequence ofcomponents to execute on the document.
 3. The method of claim 2 whereinthe configuration file further includes configuration data correspondingto each of the first component and the second component.
 4. The methodof claim 3 wherein execution of the first component includes performinga first action on the document based on the configuration data.
 5. Themethod of claim 4 further comprising modifying the configuration data,wherein the first component performs a second action on the documentbased on the modified configuration data.
 6. The method of claim 5further comprising modifying the configuration data wherein the firstcomponent is executed after the second component is executed responsiveto the modified configuration data.
 7. The method of claim 5 furthercomprising modifying the configuration data wherein the sequence ofcomponent to execute on the document is modified based on the modifiedconfiguration data.
 8. The method of claim 1 wherein the configurationdata specifies at least one of components to be loaded, a sequence ofexecution of the components, or configuration data for the components.9. The method of claim 1 further comprising receiving an object from thefirst component, the object including an editable document and a stringindicating a topic being built.
 10. The method of claim 9 furthercomprising executing at least one of the first component or the secondcomponent for each topic corresponding to a topic ID string in amanifest file.
 11. The method of claim 1 wherein at least one of thefirst component or the second component includes one or more of anaction component, a flow control component or a diagnostic component.12. The method of claim 11 wherein the at least one of the firstcomponent or the second component includes one or more of an actioncomponent, the action component including one or more of a copy fromfile, a copy from index, a transform, or a save component.
 13. Themethod of claim 11 wherein the at least one of the first component orthe second component includes one or more of a flow control component,the flow control component including one or more of an IfThen componentfor executing a configurable set of sub-components depending on a resultof an expression or a ForEach component for executing a set ofsub-components once for each node returned by an expression.
 14. Themethod of claim 11 wherein the at least one of the first component orthe second component includes one or more of a diagnostic component, thediagnostic component including one or more of a print or a validationcomponent.
 15. A method of creating a document, the method comprising:accessing a configuration file; assembling a plurality of componentsbased on the configuration file, each of the components for performingan action on a document; executing one or more actions on the documentby each of the assembled components to generate an output document, theexecuting based on the configuration file; and outputting the outputdocument.
 16. The method of claim 15 wherein executing the one or moreactions on the document by each of the assembled components includesexecuting each of the components in the plurality of components in asequence, the sequence being based on the configuration file.
 17. Themethod of claim 15 wherein executing the action on the document by eachof the assembled components includes executing a first component in theplurality of components at least a first time and a second time.
 18. Themethod of claim 17 wherein executing the first component includesperforming a first function during the first time execution and a secondfunction during the second time execution, the first function beingdifferent from the second function and being based on the configurationfile, wherein the first time and the second time are not consecutive.19. The method of claim 17 further comprising modifying theconfiguration file, wherein the modified configuration file causes acorresponding change in one of assembling the plurality of components orexecuting the one or more actions on the document.
 20. One or morecomputer readable storage media including computer readable instructionsthat when executed by a computing device perform operations comprising:receiving configuration data that indicates a plurality of components;instantiating the plurality of components based on the configurationdata, each of the components for performing an action on a documentdefined by the configuration data; executing one or more actions on thedocument by each of the assembled components to generate an outputdocument, the assembled components executed in a sequence defined by theconfiguration data; and outputting the output document.